Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

ryc_relationship table — rycre

This table stores relationship information for tables in the Repository and application databases built using Progress Dynamics.

Table 4–27 lists the table’s FLA, fields, and foreign keys.

Table 4–27: ryc_relationship table informationt 

Table FLA	Fields (data type)	Foreign keys
rycre	relationship_obj (Decimal) relationship_reference (Character) relationship_description (Character) parent_entity (Character) child_entity (Character) primary_relationship (Logical) identifying_relationship (Logical) nulls_allowed (Logical) cardinality (Character) update_parent_allowed (Logical) parent_delete_action (Character) parent_insert_action (Character) parent_update_action (Character) parent_verb_phrase (Character) child_delete_action (Character) child_insert_action (Character) child_update_action (Character) child_verb_phrase (Character) model_external_reference (Character)	relationship_obj

Table 4–28 gives details of the table’s indexes.

Table 4–28: ryc_relationship index information 

Index name	Elements	Type
XPKryc_relationship	relationship_obj	Primary Unique
XAK1ryc_relationship	relationship_reference	Unique
XAK2ryc_relationship	model_external_reference	Unique
XIE1ryc_relationship	relationship_description	Nonunique
XIE2ryc_relationship	parent_entity	Nonunique
XIE3ryc_relationship	child_entity	Nonunique
XIE4ryc_relationship	primary_relationship	Nonunique

Multiple relationships can exist between the same parent and child table if required, so one of these must be flagged as the primary relationship to use initially when joining between the two tables.

The relationship reference field is unique so that it can be referenced in code if required where multiple possible relationships exist and application functionality depend on the relationship. Where the relationship reference is irrelevant, it can be automatically generated using the Progress Dynamics sequences. The fields used to join the tables in the relationship are specified in the child table ryc_relationship_field.

The attributes about the relationship map closely with the attributes supported by ERwin.The contents of this table should be automatically populated from information exported from a case tool, such as ERwin, to make synchronization of changes as automated as possible.

This table, once populated, can be used to support generic application functionality such as automatic object generation and referential integrity trigger code.